Hi @catriona-m. I'd love to handle the serialisation within the CRUD functions, but I can't see how to achieve this. When I look at the schema type definitions, I can only use standard Go types, which therefore has all the limitations that come with them. The closest option is to use a TypeMap, but that requires all object values to be of the same type. This works until we want to use nested objects, such as

  value = {
    name    = "Name"
    boolean = true
    num     = 3
    object = {
      name   = "Arthur Dent"
      number = 42
    }
  }

as this causes a panic as object can't be converted to a string. For most other properties, we know what the correct structure of the object will be and so can define the schema in advance. However, these variables will not have a consistent schema that the provider can know about in advance, which is why I resorted to making the user do the serialisation / deserialisation.

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.